Programação de Processadores Massivamente Paralelos: Uma Abordagem Prática: O Modelo de Execução SIMT e Particionamento de Warps

O SIMT (Instrução Única, Vários Fios) modelo é o coração da arquitetura de GPU. Embora você escreva código para fios individuais, o hardware os organiza em uma hierarquia de dois níveis composta por malhas e blocos. Para maximizar a eficiência, o hardware particiona ainda mais esses blocos em unidades de 32 fios chamadas warps.

1. SIMT vs. SIMD

Diferentemente do SIMD da CPU (como SSE/AVX), onde você empacota os dados manualmente nos registradores, o SIMT permite que os fios pareçam independentes. O hardware agrupa automaticamente os fios em warps, buscando uma única instrução para todos os 32 fios para executá-la em sincronia.

2. Regra de Linearização

Os programadores usam threadIdx.x, y, z para lógica, mas o hardware transforma isso em uma sequência unidimensional para agendamento:

Índice = x + (y × blockDim.x) + (z × blockDim.x × blockDim.y)

Como o eixo x é o índice que muda mais rapidamente, os fios com valores consecutivos de threadIdx.x geralmente são alocados no mesmo warp, o que é crucial para agregação de memória.

TERMINALbash — 80x24

> Ready. Click "Run" to execute.

QUESTION 1

What is the physical scheduling 'atom' (minimum unit) in NVIDIA's SIMT model?

A single Thread

A Warp (32 threads)

A Streaming Multiprocessor

A Grid

QUESTION 2

In an 8x8 thread block, which threads will be assigned to Warp 0?

Threads with linear IDs 0 through 31

Threads with y=0 and y=1

Only threads where x=0

All 64 threads belong to Warp 0

QUESTION 3

How does SIMT differ from traditional SIMD (like SSE/AVX)?

SIMT requires manual packing of vector registers.

SIMT allows threads to operate independently at the software level while hardware manages vectorization.

SIMD is only for GPUs; SIMT is for CPUs.

There is no difference; they are synonymous.

QUESTION 4

Using the linearization formula, what is the ID of T(2, 1, 0) in a block with blockDim.x=16 and blockDim.y=16?

QUESTION 5

What happens if threads within a warp take different execution paths (e.g., an if-else statement)?

The warp executes all paths in parallel without penalty.

The warp splits into two warps.

The hardware serializes the paths, disabling threads not on the current path.

The kernel crashes.

Architectural Analysis: Linearization and Bandwidth

Applying Warp Partitioning to Matrix Addition

You are optimizing a matrix addition kernel on a 2D grid. The threads are organized into 8x8 blocks. You are considering using shared memory to improve performance.

1. [Reading Context: Figure 6.1 shows an example of placing threads of a two-dimensional (2D) block into linear order.] Draw out/Represent the partitioning of an 8x8 thread block into warps. Which thread index (x,y) marks the end of Warp 0?

Solution:
In an 8x8 block (64 threads), threads are linearized using $Index = tx + (ty \times 8)$. Warp 0 covers Linear IDs 0 to 31. T(0,0) is ID 0. ID 31 is calculated as $tx=7, ty=3$ ($7 + 3 \times 8 = 31$). Therefore, Warp 0 starts at $T(0,0)$ and ends with $T(7,3)$. Warp 1 begins at $T(0,4)$ (ID 32) and ends at $T(7,7)$ (ID 63).

2. Consider the matrix addition where each element of the output matrix is the sum of the corresponding elements of the two input matrices. Can one use shared memory to reduce the global memory bandwidth consumption? Explain with details (approx. 150 words).

Solution:
No, shared memory cannot reduce global memory bandwidth for matrix addition. In matrix addition, each output element $C[i][j]$ is the sum of $A[i][j] + B[i][j]$. Each element from the input matrices $A$ and $B$ is accessed exactly once by exactly one thread to compute its unique output. Shared memory is a high-speed scratchpad designed for data reuse—where multiple threads within a block read the same global memory address repeatedly (as seen in matrix multiplication). Since there is zero data commonality between threads in matrix addition, loading data into shared memory first would actually increase overhead. It would require one global load to shared memory, a `__syncthreads()` barrier, and then a shared memory load before the addition. This adds instruction count and synchronization latency without decreasing the number of global memory transactions. To optimize matrix addition, one should focus on global memory coalescing rather than shared memory utilization.